home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: chang.unx.sas.com!walker
- From: walker@chang.unx.sas.com (Doug Walker)
- Subject: Re: Shared Lib problems
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DnsqB3.98u@unx.sas.com>
- Date: Tue, 5 Mar 1996 13:18:39 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <65641284%agos001@pn.itnet.it> <DnJEs1.Lr0@unx.sas.com> <65641307%agos001@pn.itnet.it>
- Organization: SAS Institute Inc.
-
- In article <65641307%agos001@pn.itnet.it>,
- Stefano Agostinelli <agos001@pn.itnet.it> wrote:
- >> to see more information. Your exact link command line (whether with SC or
- >> SLINK) would help, as would the error or warning message(s) that you are
- >> getting.
- >
- > Command I use is:
- > "slink ... lib:amiga.lib lib:sc.lib ..."
- > or
- > "sc ... link lib=small.lib ...".
-
- You should use either
-
- slink ... lib lib:sc.lib lib:amiga.lib ...
-
- or
-
- sc ... link ...
-
- (do not specify any libraries on the sc command line.)
-
- The documentation clearly states that if you use SLINK to link, you should
- link with sc.lib BEFORE amiga.lib if you are using functions from sc.lib.
- See page 15 of the 6.50 Library Reference Manual. The order of the
- libraries does make a BIG difference.
-
- If you use SC to link, SC automatically adds the correct SAS/C provided
- libraries and amiga.lib to your link line. The only link libraries you
- should specify are ones that you create. I suggest using SC LINK to link
- instead of using the SLINK command directly, since there is less chance
- of getting the options wrong.
-
- --
- ***** / walker@unx.sas.com
- *|_o_o|\\ Doug Walker< BIX, Portal: djwalker
- *|. o.| || \ AOL: weissblau
- | o |//
- ======
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-